-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: update metrics Result to be MetricResult #2241
refactor: update metrics Result to be MetricResult #2241
Conversation
8321fda
to
46c6f62
Compare
@cijothomas as we discussed in #2221 I opened this to address one of the bullets brought up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
edit: We can have a single, consolidated changelog after #1042.
this is consistent with LogResult and TraceResult
bb55188
to
2c0e00f
Compare
so I should omit adding a changelog update on this pr in favor of waiting for 1042? |
this is consistent with LogError and TraceError
2c0e00f
to
72a012c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. As discussed in the PR already, we need to re-evaluate custom Error types and only make the relevant ones as public.
related to comment: #2221 (comment)
Changes
Make the
MetricResult
/MetricError
consistent withLogResult
/LogError
, andTraceResult
/TraceError
Another option could be to have all signals type be
Result
/Error
, and determine which one is used from the module pathmetrics::Result<()>
/metrics::Error
?Merge requirement checklist
CHANGELOG.md
files updated for non-trivial, user-facing changes